If you have comments about the product or this document, address them to:
Instantiations, Inc.
18101 Boones Ferry Rd, Suite 200
Portland, OR 97224
You can fax comments to (503) 684-8355 or email to vast-support@instantiations.com.
Instantiations, Inc.
18101 Boones Ferry Rd, Suite 200
Portland, OR 97224
You can fax comments to (503) 684-8355 or email to vast-support@instantiations.com.
Disclaimer: References to the OS/2 platform are included for historical reasons. Their inclusion does not represent Instantiation's support for VA Smalltalk on that platform
The following terms are trademarks of the IBM(R) Corporation in the United States, other countries, or both:
Windows(R) is a trademark of Microsoft Corporation.
UNIX(R) is a registered trademark of The Open Group in the United States, other countries or both.
|
VA Smalltalk uses construction from parts to develop software by assembling and connecting reusable components called parts.
|
||
|
Do not save the image.
|
||
|
Refer to the VA Smalltalk User's Guide.
|
||
|
The status area displays Category: Data Entry.
|
||
|
VA Smalltalk programming objects, such as attributes, actions, events, composite parts, and script names
|
||
|
For the customer name, type John Doe
|
Please take a few moments to tell us what you think about this book. The only way for us to know if you are satisfied with our books or if we can improve their quality is through feedback from customers like you. Please, go the VA Smalltalk web page and give us your feedback.
VA Smalltalk Version 7.5 includes the following changes to the installation procedure. See the readme file for additional details.
This chapter guides you through installing VA Smalltalk on Windows, OS/2, and UNIX platforms. If you are migrating from a previous version of VA Smalltalk, please refer to the VA Smalltalk Migration Guide before starting the installation.
|
1.
|
To install VA Smalltalk Manager on Windows, run setup.exe from the CD directory, i.e.
To install VA Smalltalk Client on Windows, run setup.exe from the CD directory, i.e.
To install VA Smalltalk Manager on OS/2, run install.cmd from the CD directory, i.e.
To install VA Smalltalk Client on OS/2, run install.cmd from the CD directory, i.e.
|
1.
|
For late breaking information, click on the View Readme push button.
|
2.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise, select Decline and exit the installation program.
|
|
4.
|
You will now be asked to complete the installation. Verify that all of the information is correct and click Next. The product will now install.
|
Record the path where the manager is installed. Each person installing a VA Smalltalk Client will need to know the path where the manager is installed and the IP address or alias of the server where the manager is installed. For example, if you specify f:\vast, then the manager will be named f:\vast\manager\mgr75.dat.
|
5.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
• Backup the manager file regularly.
• Run library statistics utilities on a regular basis to ensure the integrity of the manager file.
• Protect the manager file.
|
•
|
The absolute path for the library manager on the server machine. The drive letter must be the drive letter on the server machine, not the mapped drive letter for the server machine.
|
|
1.
|
For late breaking information, click on the View Readme push button.
|
2.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise, select Decline and exit the installation program.
|
|
4.
|
Click Next to continue
|
|
5.
|
Select EMSRV as the Library Access Method by which you will connect to the Library Manager. Select Next to continue. On the EMSRV client parameters window, do the following:
|
|
b.
|
Specify the fully qualified path on the server where the library manager is installed.
|
For example, if the manager is installed on a machine named vastmgr in the directory f:\vast\manager\mgr75.dat. Even if you have vastmgr mapped as M: on your computer, you would specify f:\vast\manager\mgr75.dat as the path on the server where the library manager is installed.
|
c.
|
Select Next.
|
|
6.
|
|
7.
|
Verify the information, then select Next to finish installing the VA Smalltalk Client.
|
|
8.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
|
1.
|
For late breaking information, click on the View Readme push button.
|
2.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise, select Decline and exit the installation program.
|
|
b.
|
Check to make certain that the destination folder is correct. If you wish to change the default, click the Browse push button and change the location by either clicking on a new folder or directly typing the directory in the entry field. Click OK.
|
|
d.
|
Click Next to continue.
|
|
4.
|
You will now be asked to complete the installation. Verify that all of the information is correct and click Next. The product will now install.
|
|
5.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
|
1.
|
For the latest information, click the View Readme button at the bottom of the Welcome window.
|
2.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise Decline and exit the installation.
|
|
4.
|
Check to make certain that the destination folder is correct. If you wish to change the default, click the Browse push button and change the location by either clicking on a new folder or directly typing the directory in the entry field. Click OK.
|
|
5.
|
Click Next to continue.
|
|
6.
|
Select Standalone development using File I/O. Select Next to continue. Configure the File I/O connectivity. You will need to know where the manager is installed on your local drive. Select Next.
|
|
7.
|
|
8.
|
Verify the information, then select Next to finish installing VA Smalltalk.
|
|
9.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
|
6.
|
For late breaking information, click on the View Readme push button.
|
7.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise, select Decline and exit the installation program.
|
|
b.
|
Check to make certain that the destination folder is correct. If you wish to change the default, click the Browse push button and change the location by either clicking on a new folder or directly typing the directory in the entry field. Click OK.
|
|
d.
|
Click Next to continue.
|
|
9.
|
You will now be asked to complete the installation. Verify that all of the information is correct and click Next. The product will now install.
|
|
10.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
|
10.
|
For the latest information, click the View Readme button at the bottom of the Welcome window.
|
11.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise Decline and exit the installation.
|
|
13.
|
Check to make certain that the destination folder is correct. If you wish to change the default, click the Browse push button and change the location by either clicking on a new folder or directly typing the directory in the entry field. Click OK.
|
|
14.
|
Click Next to continue.
|
|
15.
|
Select Standalone development using File I/O. Select Next to continue. Configure the File I/O connectivity. You will need to know where the manager is installed on your local drive. Select Next.
|
|
16.
|
|
17.
|
Verify the information, then select Next to finish installing VA Smalltalk.
|
|
18.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
To start the Documentation Server from the shortcuts, select VA Smalltalk Client 7.5 and then Start the Documentation Server.
To use the shared documentation server, client web browsers must replace localhost with myhostname in the URL used to access the VA Smalltalk documentation. You only need to make this change for the initial URL. Change the following:
To start the Information Center and access documentation from the shortcuts, select VA Smalltalk Client 7.5 and then Information Center.
To stop the documentation server, select Shutdown the Document Server from the Information Center main screen.
To start the documentation server on OS/2, do the following:
To start the Documentation Server from the shortcuts, select VA Smalltalk Client 7.5 and then Start the Documentation Server.
To use the shared documentation server, client web browsers must replace localhost with myhostname in the URL used to access the VA Smalltalk documentation. You only need to make this change for the initial URL. Change the following:
To start the Information Center and access documentation, select the Information Center.
To stop the documentation server in, select Shutdown the Document Server from the Information Center main screen.
|
1.
|
From the Start Menu, select Control Panel > Add/Remove Programs. Select the VA Smalltalk product you installed, then select Remove
|
|
2.
|
Click Next to continue.
|
|
3.
|
After the uninstall program is finished, click Finish to exit the uninstall program.
|
|
1.
|
Double-click on the Uninstall VA Smalltalk Enterprise client or manager icon in the VA Smalltalk folder.
|
|
2.
|
Click Next to continue.
|
|
3.
|
After the uninstall program is finished, click Finish to exit the uninstall program.
|
|
1.
|
On a UNIX platform, you must create the installation directory, e.g. /usr/local/VASmalltalk/7.5 directory before running the install.
|
|
4.
|
Create the path /usr/local/VASmalltalk/7.5 if it does not already exist.
|
|
5.
|
Run setup.
|
|
o
|
From the shell command line, run xterm -sb -e ./setup&
|
|
6.
|
To install the manager, see Installing the library manager. To install the client, see Installing a client.
|
|
1.
|
On the Welcome window, select View Readme to view the readme file for any late-breaking information on the UNIX version of VA Smalltalk.
|
|
2.
|
On the License Agreement window, read the license agreement. If you agree to the terms and conditions, select Accept. Otherwise select Decline and exit the installation.
|
|
3.
|
On some Unix platforms, problems have been reported on the Select Features screen. After selecting a new feature to install, sometimes the Next button is not enabled due to an error in synchronization of the features. To correct this problem, select the Back button and then on the License Agreement screen, select the Accept button. The Next button on the Select Features screen should then be enabled.
|
4.
|
You will now be asked to complete the installation. Verify that all of the information is correct and click Next. The product will now install.
|
|
5.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
The files are installed to /usr/local/VASmalltalk/7.5 directory.
The size of the library manager will grow considerably as source code accumulates during the course of a development effort. It is possible to install the library manager on a filesystem other than /opt, and to run the EMSRV daemon with the library manager on the alternate filesystem. This may be a convenient configuration for managing the growth of the library manager and for maintenance backups.
To install the library manager on an alternate filesystem you must complete a couple of steps manually. Before performing the install, create a /usr/local/VASmalltalk/7.5/manager filesystem which is mounted on a logical volume other than the volume on which /usr is mounted and define /usr/local/VASmalltalk/7.5/manager as a symbolic link to a directory on such an alternate filesystem.
• Backup the manager file regularly.
• Run library statistics utilities on a regular basis to ensure the integrity of the manager file.
• Protect the manager file.
We have seen rare cases where the client installation program on Linux will hang and become unresponsive after only partially completing the install. We have only noticed this on machines whose hard drive is one giant partition located at /. If this happens, a safe workaround is to terminate the install program and completely delete everything in the /usr/local/VASmalltalk/7.5 directory. Then restart the install.
|
1.
|
On the Welcome window, select View Readme to view the readme file for any late-breaking information on the UNIX version of VA Smalltalk.
|
|
2.
|
Read the License Agreement. If you agree to the terms and conditions, select Accept. Otherwise, Decline and exit the installation.
|
|
3.
|
On some Unix platforms, problems have been reported on the Select Features screen. After selecting a new feature to install, sometimes the Next button is not enabled due to an error in synchronization of the features. To correct this problem, select the Back button and then on the License Agreement screen, select the Accept button. The Next button on the Select Features screen should then be enabled.
|
4.
|
You will now be asked to complete the installation. Verify that all of the information is correct and click Next. The product will now install.
|
|
5.
|
When the installation is complete, click Finish to end the install program or View Readme to view the readme file.
|
The files are installed to the /usr/local/VASmalltalk/7.5 directory.
If you want to change your network configuration, the Smalltalk image start-up configuration file abt.ini will need to be modified. Specifically, you will need to verify that the EmLibraryInterface parameters, ServerAddress and DefaultName match you network configuration.
For more options on starting EMSRV, type emsrv -h at a command prompt.
Before you shut down your system or uninstall VA Smalltalk, you should stop the EMSRV process by issuing the command: /usr/local/VASmalltalk/7.5/bin/emadmin stop.
The user id running the documentation server must have read access to /usr/local/VASmalltalk/7.5/help and the files therein. You do not need to be root to run the documentation server.
To stop the documentation server in Unix, select Shutdown the Document Server from the Information Center main screen.
Each VA Smalltalk developer requires certain files in their own working directory. A copy of the appropriate files may be obtained by running the program /usr/local/VASmalltalk/7.5/bin/vasetup. Since a symbolic link to this program is installed in /usr/bin, users can simply run vasetup75.
When you run vasetup, VA Smalltalk copies the master abt.ini file to your working directory. If the system administrator makes any additional changes to the master abt.ini file, the copy of abt.ini that is in your working directory will not match the master abt.ini in /usr/local/VASmalltalk/7.5/newimage. If you have not made any changes to your personal copy of abt.ini, then you can just copy the new master version from /usr/local/VASmalltalk/7.5/newimage into your image directory. Otherwise you will need to manually edit your personal copy of abt.ini to pick up any important new information from the master version of abt.ini.
On Unix you can customize some of the default look and feel of your VA Smalltalk development environment. This can be accomplished by placing an ENVY application defaults file into your home directory. A sample ENVY application defaults file can be found in the directory /usr/local/VASmalltalk/7.5/app-defaults. Copy this file to your home directory and then make changes to suit your tastes.
EMSRV supports repositories of up to 16 GB. The actual size limit may be smaller depending on the capabilities of the file system or operating system where EMSRV is running. Refer to the EMSRV installation for your operating system documented in this Installation Guide for more information.
|
•
|
Removed -n option to disable tracking of statistics. Statistics are now always tracked.
|
|
•
|
Removed -w option to track locks. Locks are now always tracked.
|
|
•
|
Removed -rd option on PC platforms to disable authentication. Authentication is disabled by default.
|
|
•
|
|
•
|
|
•
|
Added -a option on PC platforms to change the timeout for killing connections that are inactive with a lock.
|
|
•
|
Removed -lp option on UNIX platforms to set timeout for killing connections that are inactive with a lock.
|
|
•
|
For UNIX platforms, removed all code associated with device numbers including -xd option. EMSRV will now check the filesystem type and reject any path residing on a filesystem of type nfs for AIX, HP-UX, and Solaris; or type 0x6969 (NFS_SUPER_MAGIC) for Linux.
|
|
o
|
EMSRV uses TCP/IP for its client/server network connections. The default limit for client connections to a server is 512. The default limit for client connections can be changed by using the -M command line option when starting EMSRV. Theoretically, the number is bounded primarily by memory, but testing has shown that some TCP/IP stacks will run out of stream sockets before this limit of memory is reached. Typically, this number is greater than one hundred but it varies with each stack.
|
•
|
Specify VA Smalltalk user IDs and passwords for all users of VA Smalltalk. This option requires the maintenance of a passwd.dat file, plus the use of the -rp option when starting EMSRV.
|
|
•
|
Use the native operating system user names and passwords for all users of VA Smalltalk. This option requires the use of the -rn option when loading EMSRV and no maintenance of a passwd.dat file.
|
If you intend to maintain VA Smalltalk user IDs on your site, you must create and maintain a passwd.dat file in the working directory.
The passwd.dat file should have its access rights restricted so it cannot be read or written by regular VA Smalltalk users.
The following shows an example of a passwd.dat file:
If you are using passwd.dat checking, you can look in that file to locate the Library Supervisor's password. If there is not a password specified, you may at this point add one.
|
2.
|
Start a client image. Select Tools >Users>Modify to change the Network Name of the Library Supervisor to a userid that is already defined on your network.
|
|
4.
|
Most native authentication services on UNIX platforms offer multiple options for configuration. The simplest form of native authentication on UNIX platforms is the local password file (usually /etc/passwd) which contains passwords encrypted with a one-way encryption function. Although the passwords cannot be decrypted, the file is readable by all users of the system and therefore susceptible to dictionary-based password cracking attempts.
The simplest alternative to the local password file is password shadowing. On systems that use NIS/yp or password shadowing, replace each encrypted password in the /etc/passwd file with a special token and store the passwords in a separate file not readable by normal system users.
Previous releases of EMSRV for UNIX platforms supported local password files and shadow passwords by using two separate EMSRV executables: emsrv and emsrv.shadow. This was necessary because each authentication system uses a different programming interface.
Recent releases of most UNIX platforms now offer a single authentication programming interface that can support both of the aforementioned authentication systems as well as many others. The most well-known of these authentication frameworks is PAM (password Authentication Modules). PAM was developed by Sun Microsystems and is now supported by and ships as part of Solaris, Linux, and HP-UX. Although there is no PAM implementation included with AIX, IBM offers a similar authenticate() function that can be used to authenticate users using local password files, shadow passwords, and DCE authentication.
A single authentication programming interface makes it possible for one EMSRV executable to use a variety of authentication systems. For this reason, there is no longer an emsrv.shadow available on some UNIX platforms. In such cases, the emsrv executable can be used to authenticate using shadow passwords and, potentially, other forms of authentication as well.
Where EMSRV uses an authentication framework such as PAM, the authentication system used by EMSRV and its exact configuration, are determined by the environment. For example, EMSRV for Linux uses PAM and, therefore, requires the file /etc/pam.d/emsrv to be present and to specify the PAM (module) used by EMSRV.
EMSRV for AIX now supports authentication using the system authenticate() function. This allows one EMSRV executable to support both shadowed and non-shadowed passwords in addition to DCE authentication.
The authentication method for each user is set in the /etc/security/user file.
PAM must be correctly configured on a machine running EMSRV otherwise it will not even be possible to shutdown EMSRV using EMADMIN. The PAM configuration file must be copied to /etc/pam.d/emsrv. A sample PAM configuration file is included with this release (see /usr/local/VASmalltalk/7.0/samples/PAM).
There is a bug in the Solaris 2.6 implementation of PAM that prevents EMSRV from working correctly. The patch 106257-05 must be applied when using EMSRV with Solaris 2.6. The patch is available at: http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fpatches%F106257&zone_32=PAM
PAM must be correctly configured on a machine running EMSRV otherwise it will not even be possible to shutdown EMSRV using EMADMIN. The /etc/pam.conf file is included with this release (see /usr/local/VASmalltalk/7.0/samples/PAM).
EMSRV is setup to run on KIRA\NT4PDC. Users in both domains can be authenticated. Account names may be specified using a simple name in which case EMSRV will locate the domain containing the user, or the domain may be specified using a SAM-compatible name such as CHIEF\ADRIAN.
OS/2 does not support any native authentication method. The only available authentication option is to use a passwd.dat file and the -rp commandline option when starting EMSRV.
On Windows and OS/2, do not use a mapped network drive.
On UNIX, do not use a remote NFS file system.
EMSRV has the file access rights of the EMSRV account for PC platforms or the account that starts EMSRV under UNIX. This means that the EMSRV account must have access rights to all directories and files that VA Smalltalk users require. To ensure the integrity of the library file manager.dat, the access rights for this file may be restricted to the EMSRV account.
|
The EMADMIN command you are issuing.
|
|
|
EMADMIN has one option, the port number, -P<port number>. This parameter specifies the port that EMSRV is using instead of the default. The default port number is 4800. This option is available for all EMSRV commands.
|
|
To send the list of current connections to EMSRV running on the local machine to the file clist.txt, enter:
The copy command allows you to copy one repository, the source, to another repository, the target. The target repository can be on the same EMSRV server as the source, or on a different EMSRV server that is on the same network.
The copy command locks the library to ensure that the library cannot be changed while it is being copied.
To use the copy command, the following conditions must exist:
|
•
|
To run the copy command in a batch file, the password may be specified as part of the command line. This, in conjunction with the -q (quiet) option, ensures that no prompting occurs during the batch process.
|
|
<ip_address> is optional and specifies the host that EMSRV is running on. It can be either the file server IP host name or its Internet address. If a host name is not provided, localhost is used.
<file name> is required and is the file specification.
|
|
The copy command default behavior does not overwrite an existing file. Normally, you are prompted for overwrite permission. The -o option specifies that the destination file may be overwritten without prompting.
|
|
|
This specifies the password to use when the copy command is validating access to the source database. The password cannot contain spaces.
|
|
|
By default, the copy command prints the number of bytes transferred during the copy operation. The -q option indicates "quiet operation" and the transfer count is not printed. When this option is enabled, you will not be prompted about potential problems from low disk space.
|
|
This example copies (in quiet mode) manager.dat to test.dat in the working directory, overwriting test.dat if it exists and using the password "secret" to access the source library.
The list command lists current connections for to a repository server. This command sends a message to the host running EMSRV and requests the list of connections. Information about connection statistics and active locks can be obtained using the list command modifiers.
To verify that all clients are disconnected, use the list operation before stopping EMSRV.
The list command has the following modifiers:
|
Displays the statistics for the connection specified by <connection number>.
|
|
|
Displays the active locks for the connection specified by <connection number>.
|
|
The opts command enables you to display the current options for a repository server and change the logging level for the repository server.
The stat command displays the statistics for operations completed since the repository server was started. This command also tells you what the current EMSRV working directory is.
The stat command sends a message to a host running EMSRV and requests a copy of the latest statistics. This command provides information such as numbers of file opens, closes, and writes.
The stop command shuts down EMSRV remotely or closes a client connection to EMSRV. When you use this operation to shut down EMSRV, you are prompted for the EMSRV account password. The password characters are not displayed on the screen. EMSRV can be shut down only if you have entered the correct password. The stop command can also be used to terminate a connection that can no longer communicate with the client. Use the list command to obtain the list of connections and their respective connection numbers that can be closed.
The stop -k <connection number> command is used to close a client connection to EMSRV.
|
1.
|
Verify that TCP is installed and correctly bound to a network adapter. You can verify the binding by using the ping utility to communicate with the Windows NT/2000 machine from a workstation on the LAN.
|
EMSRV uses an existing Windows account to provide file access restrictions. The Windows account name used by EMSRV is referred to as the EMSRV account name, and the password for that account is referred to as the EMSRV account password. Both the Windows account from which EMSRV is started (that is, if EMSRV is not started as a service) and the EMSRV account must be granted the advanced user right Act as part of the operating system and be a member of the Administrators group.
|
2.
|
Run the User Manager utility by selecting Administrative Tools (Common) > User Manager from the Start menu.
|
|
3.
|
Select the EMSRV user and then select Polices > User Rights. The User Manager window opens.
|
|
4.
|
|
5.
|
Select the check box Show Advanced User Rights.
|
|
6.
|
|
7.
|
Select the Add push button and add the EMSRV user to the list.
|
|
8.
|
Select OK to save your choices and close the open windows.
|
|
3.
|
Select Local Security Policy > Local Policies > User Rights Assignment > Act as part of the operating system.
|
|
4.
|
Click on the Add push button and add the EMSRV user to the list.
|
|
5.
|
Click on the Add push button to add the user and save your choices.
|
For Windows 2000 Server and Windows 2003 Server, the Local Security Policy may be overridden by the Domain Controller Security Policy or the Domain Security Policy. User rights for the domain controller and/or domain may need to be set in order for the Effective Policy Setting in the Local Security Policy to appear checked.
For Windows 2000 Advanced Server, there is no Local Security Policy. Assign the right for the Domain Controller Security Policyand Domain Security Policy as necessary.
|
•
|
To start and stop EMSRV as a service, the EMSRV account must have the Log on as a service user right set and the Deny logon as a service user right NOT set.
|
|
•
|
To start and stop EMSRV interactively or from a batch file, the EMSRV account must have the Log on locally user right set and the Deny logon locally user right NOT set.
|
|
•
|
Each client authenticated by EMSRV must have the Access this computer from the network user right set for the account used by that client. For each account, you must also ensure that the Deny access to this computer from the network right is NOT set.
|
|
1.
|
|
2.
|
|
•
|
|
•
|
Sets the working directory to d:\path, The working directory is where EMSRV writes a log file.
|
The following steps cover how to install EMSRV as a Windows service. See Troubleshooting EMSRV as a Windows service for a listing of common problems and solutions when running EMSRV as a Windows service.
|
1.
|
|
2.
|
Enter emsrv -install <parameters>. The optional <parameters> are EMSRV parameters such as -u <user name>, -p <password>, and so on. (For a list of available parameters, see EMSRV Startup options.) These parameters are fixed and will be used every time EMSRV is started as a service.
|
Ensure that -install is the first parameter. This installs EMSRV as a service in the registry and copies the necessary DLLs to the system directory. If there is an older version of EMSRV already installed, it removes the older version and installs the new version.
|
i.
|
Open the Control Panel and double-click the Services control panel.
|
On Windows 2000, Windows XP, and Windows Vista you access the Services control panel via the Administrative Tools icon within the Control Panel.
|
ii.
|
Select the EMSRV Service in the Services control panel.
|
|
iii.
|
Select HW Profiles and verify that a configuration is enabled. Enable one if necessary.
|
|
iv.
|
Select Start and EMSRV will start as a service. (Selecting Stop will stop the service and close all connections.)
|
|
i.
|
Enter sc start EMSRV -u <user name> -p <password> at a DOS command prompt.
|
|
ii.
|
Query the service status by entering sc query EMSRV.
|
To stop the service, enter sc stop EMSRV.
sc.exe is available with the Windows NT/2000 Resource Kit.
|
i.
|
Go to the Services control panel.
|
|
ii.
|
Select EMSRV and press the Startup button.
|
|
iii.
|
Select Automatic for the startup type.
|
To remove the EMSRV Service from the registry, enter EMSRV -remove at a DOS command prompt. Alternatively, you can remove it by entering sc delete EMSRV.
The -remove option will stop the service if it is running as well as delete it from the registry.
|
•
|
The stop command will stop the service, closing all active connections without warning.
|
|
•
|
Parameters entered at the Services control panel are ignored. Enter all parameters when installing with the -install option.
|
|
The error message An internal Windows NT error has occurred appears at startup
|
Open the Services control panel. Verify that the startup parameters are entered correctly and the user name is a valid user on the server. The -u option is always needed to start the server.
|
|
The error message The specific service is disabled and cannot be started appears at startup
|
From the Control Panel, select Services and then the HW Profiles button. Select the Original Configuration. If its status is disabled, enable it by selecting the Enable button.
|
|
The service could already be running on the local machine. Otherwise the service could be disabled. Select EMSRV Service in the Services control panel. Select Startup to open the Service window. Select Automatic or Manual for Startup Type.
|
|
|
The error message The service did not start due to a logon failure appears at startup
|
An invalid password was entered in the Service window of the Services control panel, which you access by selecting Startup. Open the Service window and change the password or log on as the System Account.
|
|
The error message The process terminated unexpectedly appears at startup
|
|
|
The error message Access Denied appears when installing the service.
|
The user must have write access to the \Windows\system32 directory so that the message file can be copied from <varoot>\bin to the \Windows\system32 directory.
|
|
2.
|
Verify that TCP is installed and correctly bound to a network adapter. You can verify the binding by using the ping utility to communicate with the OS/2 EMSRV computer from a workstation on the LAN.
|
|
1.
|
|
2.
|
This command starts EMSRV with the working directory c:\manager and logs messages to the console.
Note on starting EMSRV
may get the message SYS1041: The name EMSRV is not recognized as an internal or external command, operable program or batch file. To bypass this problem, issue the command sequence without the START:
|
2.
|
Verify that the NetWare TCPIP NLM is loaded and correctly bound to a network adapter. You can verify the binding by using the ping utility to communicate with the NetWare file server from a workstation on the LAN. When EMSRV for NetWare is started, if this NLM is not loaded, it will automatically load. EMSRV for NetWare will also automatically load the NWSNUT.NLM which is required by the EMSRV for NetWare user interface.
|
The EMSRV NLM logs on to the NetWare file server using an existing NetWare account and password to provide file access restrictions. The NetWare account name used by EMSRV is referred to as the EMSRV account name, and the password for that account is referred to as the EMSRV account password.
|
3.
|
Change directory to the directory containing the EMSRV executable, sys:\system (as specified previously).
|
|
4.
|
Start EMSRV. At the file server console, enter load emsrv with the desired parameters (see EMSRV Startup options).
|
|
•
|
|
•
|
Sets the working directory to volname:\path.
|
You can add an appropriate command line to the file server autoexec.ncf file to automatically load NLM when the NetWare file server is rebooted.
When you select Change Settings, a form is displayed that you can view and edit. To exit the form and save the changes (which implements them), press Esc.
|
-w (default: 512)
|
||
|
Displays the current reporting level. To change the reporting level, press Enter to access a pop-up menu.
|
-s0 (logs all operations)
-s1(logs warning and error messages)
-s2 (default: logs only error messages)
|
|
|
-t (default: yes)
|
||
|
Specifies whether client password verification is disabled, whether native NetWare passwords are used, and whether the passwd.dat file is used. To change the style of password verification, press Enter to access a pop-up menu.
|
-rn (rejects users who do not supply a valid NetWare user name and password)
-rd (default: disables password checking for clients)
-rp (rejects users who are not in the passwd.dat file)
|
|
|
(default: 1000)
|
Select View Connections to display a list of client connections. You can scroll through the list to select a specific connection. After selecting a connection:
|
•
|
Press Enter to display its statistics.
|
|
•
|
Press Delete to terminate the connection.
|
|
•
|
Press Esc to return to the menu.
|
To display EMSRV statistics, select EMSRV Statistics from the Menu Screen.
Select View Message Screen from the Menu Screen to display the Message Screen. To return to the Menu Screen, press Esc.
Select EMSRV Statistics from the Menu Screen to display EMSRV statistics that have been accumulated since the EMSRV NLM was started.
You typically display EMSRV statistics after displaying connection statistics using View Connection List.
To force a screen update, select EMSRV Statistics if the EMSRV statistics are currently displayed.
|
1.
|
Select Change Settings from the Menu Screen.
|
|
2.
|
Select Reporting Level.
|
|
3.
|
Press Enter.
|
You cannot unload EMSRV for NetWare using the unload command at the file server console. You can unload it only from the Menu Screen or by running EMADMIN. (For information on using EMADMIN, see The EMADMIN utility.)
|
1.
|
Verify that all VA Smalltalk users that were connected to EMSRV have disconnected. To verify this, select View Connection List from the Menu Screen or use EMADMIN.
|
|
2.
|
If there are connections, terminate them by selecting View Connection List from the Menu Screen and pressing Esc.
|
|
3.
|
Unload the EMSRV NLM by using EMADMIN or the Menu Screen. From the Menu Screen, select Shutdown EMSRV to shut down and unload the EMSRV NLM. You must enter the EMSRV account password before EMSRV will unload.
|
EMSRV no longer supports NetWare 4.11 or NetWare 5.0, but EMSRV can be run on those platforms if additional steps are taken. CLIBAUX.NLM must be loaded before the EMSRV NLM is loaded. CLIBAUX.NLM is included with Novell's NetWare 4.11/4.2 Support Pack 8a, but is also available separately from Novell in the file CLIBAUX1.EXE, which can be found at the following location:
http://support.novell.com/cgi-bin/search/download?/pub/updates/nw/nw42/clibaux1.exe
http://support.novell.com/cgi-bin/search/download?/pub/updates/nw/nw42/clibaux1.exe
EMSRV is installed in the bin directory under the installation directory. The standard installation directory is /usr/local/VASmalltalk/7.5.
Before you start EMSRV for UNIX, verify that you are running one of the supported UNIX operating systems. See VA Smalltalk System Requirements for currently supported platforms.
On AIX, you must enable large file support for both the volume hosting a repository and the user starting the EMSRV process. When creating a filesystem, ensure that the arguments -o bf=true are used with mkfs.
To set the limits for the user starting the EMSRV process, specify the number of 512 byte blocks as arguments on the -Hf and -Sf options of the ulimit command. Use the following commands to enable repositories up to 16 GB in size:
EMSRV for AIX authentication is implemented using the system authenticate() function. This allows one EMSRV executable to support both shadowed and non-shadowed passwords in addition to DCE authentication. The authentication method for each user is set in the /etc/security/user file.
On Solaris, filesystems automatically have large file support but limits for the user starting the EMSRV process must still be set using the ulimit command. To set the limits for the user starting the EMSRV process, specify the number of 512 byte blocks as arguments on the -Hf and -Sf options of the ulimit command. Use the following commands to enable repositories up to 16 GB in size:
EMSRV for Solaris implements authentication using PAM. PAM must be correctly configured on a machine running EMSRV otherwise it will not even be possible to shutdown EMSRV using EMADMIN. The /etc/pam.conf file must detail the emsrv service. This release includes an example pam.conf file in /usr/local/VASmalltalk/7.0/samples/PAM.
On HP-UX, large file support needs to be enabled for both the volume hosting a repository and the user starting the EMSRV process. When creating a filesystem, ensure that the argument -o largefiles is used with newfs.
To set the limits for the user starting the EMSRV process, specify the number of 512 byte blocks as arguments on the -Hf and -Sf options of the ulimit command. Use the following commands to enable repositories up to 16 GB in size:
PAM must be correctly configured on a machine running EMSRV otherwise it will not even be possible to shutdown EMSRV using EMADMIN. The PAM configuration file must be copied to /etc/pam.d/emsrv. A sample PAM configuration file is included in /usr/local/VASmalltalk/7.0/samples/PAM.
On UNIX platforms, the EMSRV process will have the file access permissions of the UNIX 4account that starts EMSRV. The UNIX account name that is used to start EMSRV is referred to as the EMSRV account name, and the password for that account is referred to as the EMSRV account password.
|
1.
|
|
2.
|
|
The file system requires read locks. The default setting is 0, which indicates the file system does not need read locks.
|
||
|
Ignores signals. <q> = ignore SIGQUIT; <t> = ignore SIGTERM. By default, either of these signals cause EMSRV to terminate.
|
||
|
Writes the log to file <name>. By default, the log is written to emsrv.log. The file <name> must specify a valid path for which the EMSRV account has sufficient access rights.
|
||
|
Logs messages to stdout instead of a log file. EMSRV must be run in the foreground using the -f option if -ls is used.
|
||
|
For NetWare, you must specify -p without the password parameter if the EMSRV account has no password.
|
||
|
The file system releases locks on file close. The default setting is 1, which indicates the file system releases locks when files close.
|
||
|
Rejects users who are not in the passwd.dat file. The default grants access to users who are not in the password file.
|
||
|
Specifies the EMSRV working directory. The directory <path> must be a valid path for which the EMSRV account has sufficient access rights to read, write, or both.
|
EMSRV contains comprehensive diagnostics. Based on the specified reporting severity level and whether file logging is enabled, statistics and diagnostic information are logged to the emsrv.log file and displayed on the console (or on the EMSRV for NetWare Message Screen). All messages with a severity level lower than the current level are suppressed. You can set the level when you start EMSRV, and you can change it dynamically, using the EMADMIN utility. The reporting levels are as follows:
|
•
|
|
•
|
|
•
|
|
o
|
|
o
|
|
o
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
